Skip to content

Conversation

End-rey
Copy link
Contributor

@End-rey End-rey commented Oct 3, 2025

Closes #3361, #3362.

@End-rey End-rey self-assigned this Oct 3, 2025
@End-rey End-rey force-pushed the 3361-move-fschain_autodeploy-out-of-top-level branch from da78f7f to aef9c30 Compare October 3, 2025 13:22
Copy link

codecov bot commented Oct 3, 2025

Codecov Report

❌ Patch coverage is 68.21705% with 41 lines in your changes missing coverage. Please review.
✅ Project coverage is 26.79%. Comparing base (c2fa56e) to head (bf59214).
⚠️ Report is 12 commits behind head on master.

Files with missing lines Patch % Lines
pkg/innerring/innerring.go 0.00% 41 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #3619      +/-   ##
==========================================
+ Coverage   26.75%   26.79%   +0.04%     
==========================================
  Files         653      653              
  Lines       51047    51111      +64     
==========================================
+ Hits        13656    13697      +41     
- Misses      36337    36362      +25     
+ Partials     1054     1052       -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

CHANGELOG.md Outdated
`neofs-adm fschain estimations` was removed.

Use new `fschain.disable_autodeploy` IR configuration option instead of deprecated `fschain_autodeploy`,
that was removed in next release.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mention that default value for the old config has changed?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

but in fact, i think it is useless work, we will just drop it in the next release, nobody gonna change this exact value in their configs, they will just use the new one


serveMetrics(server, cfg)

// TODO: remove deprecated option in future releases
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

issue?

serveMetrics(server, cfg)

// TODO: remove deprecated option in future releases
if cfg.IsSet("fschain_autodeploy") && cfg.IsSet("fschain.disable_autodeploy") &&
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think any case when both values are set can be reported as an error, this is smth abnormal to me

@End-rey End-rey force-pushed the 3361-move-fschain_autodeploy-out-of-top-level branch from aef9c30 to 1aff241 Compare October 7, 2025 21:05
@End-rey End-rey changed the title ir: move fschain_autodeploy out of top level ir: move config options out of top level Oct 7, 2025
@End-rey End-rey force-pushed the 3361-move-fschain_autodeploy-out-of-top-level branch from 1aff241 to 6f64aae Compare October 8, 2025 07:25
Copy link
Contributor

@cthulhu-rider cthulhu-rider left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems good

if cfg.IsSet("fee.main_chain") {
log.Warn("configuration option 'fee.main_chain' is deprecated, use 'mainnet.extra_fee' with the same value instead")
// default value
if cfg.Mainnet.ExtraFee == 50000000 {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

default value may be specified in the config file explicitly. This will mutate it. We should be able to distinguish this case from Viper.SetDefault(), and return an error

if cfg.IsSet("fschain_autodeploy") && cfg.IsSet("fschain.disable_autodeploy") {
return nil, fmt.Errorf("'fschain_autodeploy' and 'fschain.disable_autodeploy' set simultaneously")
}
if cfg.IsSet("fschain_autodeploy") {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

may be merged with the previous if. Not a big deal taking into account further removal of both blocks

@End-rey End-rey force-pushed the 3361-move-fschain_autodeploy-out-of-top-level branch from 6f64aae to d8d0330 Compare October 9, 2025 22:47
@End-rey End-rey force-pushed the 3361-move-fschain_autodeploy-out-of-top-level branch from d8d0330 to 0c9d9d1 Compare October 10, 2025 13:23
Copy link
Member

@roman-khimov roman-khimov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rebase, please.

Don't use viper's `SetDefault`, because it triggers configs `Set` and then we
cannot determine whether this value was in the configuration or not.

Signed-off-by: Andrey Butusov <[email protected]>
New `fschain.disable_autodeploy` IR configuration, which inverts the value of
the `fschain_autodeploy` option. Make `fschain_autodeploy` default to `true`,
support it for one more release.

Closes #3361.

Signed-off-by: Andrey Butusov <[email protected]>
@End-rey End-rey force-pushed the 3361-move-fschain_autodeploy-out-of-top-level branch from 0c9d9d1 to bf59214 Compare October 16, 2025 15:39
`mainnet.enabled` IR configuration, which inverts the value of
the `without_mainnet` option. By default, mainnet is disabled now.

Ref #3362.

Signed-off-by: Andrey Butusov <[email protected]>
Closes #3362.

Signed-off-by: Andrey Butusov <[email protected]>
@End-rey End-rey requested a review from roman-khimov October 16, 2025 15:39
@roman-khimov roman-khimov merged commit 168b71b into master Oct 17, 2025
21 of 22 checks passed
@roman-khimov roman-khimov deleted the 3361-move-fschain_autodeploy-out-of-top-level branch October 17, 2025 08:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Move fschain_autodeploy out of top level

4 participants